home *** CD-ROM | disk | FTP | other *** search
Text File | 1989-08-22 | 1.8 KB | 45 lines | [TEXT/GEOL] |
- Item 2081216 2-Aug-89 19:39
-
- From: MOOF Rollin, Keith A, APL
-
- To: MACAPP.TECH$ MACAPP Tech
-
- Sub: Re: Response to Really nasty…
-
- To: Brendan McCarthy
-
- In your last posting, you write:
-
- >Now for the (partial) flame:
- ><<flame on>>
- >I encountered this problem (and several other time-burners) while trying to
- >create a library that includes object files from a couple of my own MacApp
- >units, plain Pascal, assembly, and C. I wish the MAmake mechanism was a
- little
- >more flexible.
- >Currently, it assumes that you want an application whenever you build anything
- >with MacApp. In my case, in order to correctly create the library, I had to
- >hack the 'Build Rules and Dependencies' script to echo {PascalOptions} so I
- >could see what they were (since they are UnExported when the MAmake tool is
- >finished executing.) Then I had to use those same Pascal options to create a
- >bogus SomethingLib.MAmake file script.
- ><< flame off>>
-
- If I understand your ... uh ... comment correctly, then MABuild should be able
- to do what you want it to. Set {MAUserAutoBuild} to hold the name of the
- library you want to build, and MABuild will automatically build it (see the
- comments in the "{MacApp}Startup" file). MABuild is smart enough to create MPW
- Tools and Libraries in addition to applications. To see how this is done, take
- a look at the .MAMake file for MAcApp itself (it is, after all, just a library)
- (did I say _JUST_ a library ???) or the .MAMake files for PostRez or MABuild.
-
- Note that there is a bug in MABuild right now that prevents you from building
- more than one user library, so don't spend several hours tearing your hair out
- over that one.
-
- Hope this helps,
-
- - Keith Rollin
- - Apple Developer Technical Support
-
-